Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications

Using r-code libraries to improve r-code performance

You can organize and store r-code files in a Progress 4GL r-code library. A Progress 4GL r-code library is a collection of r-code procedures combined in a single file. R-code libraries allow you to manage and execute r-code procedures more efficiently.

OpenEdge provides two types of r-code libraries: standard and memory-mapped. A standard library contains r-code procedures that execute in local memory. A memory-mapped library contains r-code procedures that execute in shared memory. You create r-code libraries by using the PROLIB utility. For information about using the PROLIB utility to create and manage r-code libraries, see Chapter 6, " Managing R-code Libraries."

When loading and executing r-code procedures from operating system files in a directory, OpenEdge must open and close each file individually. When loading and executing r-code procedures from standard or memory-mapped libraries, OpenEdge opens only one file—the library itself—to access all of the r-code files in the library.

When you execute r-code procedures from either a standard library in local memory or a memory-mapped library in shared memory, you gain the following advantages:

Faster access to r-code.
Fewer file open and close operations.
Less I/O to temporary files.

When you execute r-code procedures from a memory-mapped library in shared memory, you gain the following additional advantages:

Even faster access to r-code.
Requires less memory because multiple clients access the same r-code segments in shared memory.